Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add ARN created roles as output #123

Merged
merged 5 commits into from
May 11, 2023

Conversation

Nekoshido
Copy link
Contributor

No description provided.

@mgerlach mgerlach merged commit c4dc148 into idealo:fork_prs May 11, 2023
mgerlach pushed a commit that referenced this pull request May 11, 2023
* Add ARN created roles as output

* terraform-docs: automated action

* Rollback Readme.md

* terraform-docs: automated action

---------

Co-authored-by: HectorArchilogic <hector@archilogic.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@mgerlach
Copy link
Contributor

@Nekoshido thanks for the PR. I just merged and released 2.4.0. Interesting that the GH workflow was able to push the doc update to your fork. Did you make any special settings?

@Nekoshido
Copy link
Contributor Author

Nekoshido commented May 11, 2023

@Nekoshido thanks for the PR. I just merged and released 2.4.0. Interesting that the GH workflow was able to push the doc update to your fork. Did you make any special settings?

Thank you for the fast response. I updated the README manually, not sure if it was that.

@mgerlach
Copy link
Contributor

mgerlach commented May 11, 2023

Yeah I

@Nekoshido thanks for the PR. I just merged and released 2.4.0. Interesting that the GH workflow was able to push the doc update to your fork. Did you make any special settings?

Thank you for the fast response. I updated the README manually, not sure if it was that.

I don't think so. Our GH PR check has a part where it updates parts of the readme with generated documentation about versions, variables and outputs. It pushed generated docs twice onto your PR branch. We had the case before where someone created a PR against main from a fork and our PR workflow was not able to push the generated doc onto the fork. This is why we came up with the fork_pr branch, where we can merge PRs even if the docs generation did not work. We then create a PR from fork_pr against main, whereupon docs are generated by the PR creation. Then we merge, thus preserving the original commits made by any contributors outside our org.

So I wonder why our GH workflow was able to push to your fork... but nevermind, merging still went smoothly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants